docs(OCM): ISignedCloudFederationProvider needed for OCM notification - #15444
Conversation
If an app sends OCM shares AND also recieves OCM notifications, it needs to implement ISignedCloudFederationProvider to be able to verify the http message signature of the notification. Signed-off-by: Micke Nordin <kano@sunet.se>
📖 Documentation Preview📄 1 changed documentation pageLast updated: Wed, 12 Aug 2026 09:36:21 GMT |
|
Hello there, We hope that the review process is going smooth and is helpful for you. We want to ensure your pull request is reviewed to your satisfaction. If you have a moment, our community management team would very much appreciate your feedback on your experience with this PR review process. Your feedback is valuable to us as we continuously strive to improve our community developer experience. Please take a moment to complete our short survey by clicking on the following link: https://cloud.nextcloud.com/apps/forms/s/i9Ago4EQRZ7TWxjfmeEpPkf6 Thank you for contributing to Nextcloud and we hope to hear from you soon! (If you believe you should not receive this message, you can add yourself to the blocklist.) |
If an app sends OCM shares AND also receives OCM notifications, it needs to implement ISignedCloudFederationProvider to be able to verify the http message signature of the notification.
Related PR:s
cause: nextcloud/server#62543
fix: nextcloud/deck#8261
🖼️ Screenshots
✅ Checklist
codespellor similar and addressed any spelling issues